If I execute, for example, ocm create ca, I get the warning:

Command "componentarchive" is deprecated, Deprecated - use CommonTransportFormat instead

But componentarchive is not a command. Unfortunately, I didn't find at first glance, how to correct the message.

Edit: it is a command. Though the message looks strange, we'll likely have to live with it.

Was it really part of #1244, to directly remove all mentions of component archive from the reference? I thought, for now we only wanted to put a disclaimer with a warning.

But I'm not against removing it. I find it a bit inconsistent, but, on the other hand, maybe it is a good motivation for existing user to start thinking of switching to CTF.

One more place to deprecate:

If I execute, for example, ocm create ca, I get the warning:

Command "componentarchive" is deprecated, Deprecated - use CommonTransportFormat instead

But componentarchive is not a command. Unfortunately, I didn't find at first glance, how to correct the message.

Edit: it is a command. Though the message looks strange, we'll likely have to live with it.

Cobra-commands do actually have a field, where you can write a string to, marking commands as deprecated. See: https://github.com/hilmarf/ocm/blob/deprecate/ComponentArchive/cmds/ocm/commands/ocmcmds/componentarchive/cmd.go#L24
There are in total three places:

Was it really part of #1244, to directly remove all mentions of component archive from the reference? I thought, for now we only wanted to put a disclaimer with a warning.

But I'm not against removing it. I find it a bit inconsistent, but, on the other hand, maybe it is a good motivation for existing user to start thinking of switching to CTF.

You're right, it's not written as requirement to remove all mentions of component archive. But I don't like to read through anyhow too large documentation and then need to let my brain filter out everything which is deprecated.

@morri-son what's your take on that? Shall we still generate all the documentation around CAs or not?

One more place to deprecate:

ocm/cmds/ocm/commands/ocmcmds/common/options/fileoption/option.go

Line 22 in 0296603

func NewCompArch() *Option {

thanks - good catch! I obviously missed to search for component-archive - for whatever reason it's written here with '-'!?!?

@hilmarf, Commands ocm add sources and ocm add resources are specific to component archives:

So far only component archives are supported as target.

So far those commands are not covered by this PR, if I see it correctly, right? There may be also other commands like this, which I'm not aware of.

A separate question is, if we remove all information about component archives, do we already have enough documentation on how to achieve the same result with CTF?

@hilmarf, Commands ocm add sources and ocm add resources are specific to component archives:

So far only component archives are supported as target.

So far those commands are not covered by this PR, if I see it correctly, right? There may be also other commands like this, which I'm not aware of.

yes, that's right - #1254 is the follow up task to be done... or we are faster with the rewrite and skip it ;-)

A separate question is, if we remove all information about component archives, do we already have enough documentation on how to achieve the same result with CTF?

I don't know. I'm not using CAs.

A separate question is, if we remove all information about component archives, do we already have enough documentation on how to achieve the same result with CTF?

as mentioned above there are some commands that only work with CAs, but personally I also never used CAs, but only CTFs and think there is enough documentation on using CTFs + component constructors. Only in case someone manually creates components step by step using resource files, he may stumble into this issue. Looking at the documentation these cases are more to explain how to build a component and its different artifacts step by step, not a use case for pipelines.

@morri-son , please check #1244 (comment)

As you see, @hilmarf suggests to remove documentation for ocm create ca and ocm transfer ca as part of this PR.

1. Do we want to do this, or do we for now only want to add a deprecation warning to the documentation?
2. Commands like ocm add sources and ocm add resources are also specific to component archives. Do we want to remove their documentation as well? Or do we want to tag them with FIXME and adapt to CTF with <User Story> - Replace CA usage in resources + download #1254?

@morri-son , please check #1244 (comment)

As you see, @hilmarf suggests to remove documentation for ocm create ca and ocm transfer ca as part of this PR.

1. Do we want to do this, or do we for now only want to add a deprecation warning to the documentation?
2. Commands like ocm add sources and ocm add resources are also specific to component archives. Do we want to remove their documentation as well? Or do we want to tag them with FIXME and adapt to CTF with - Replace CA usage in resources + download #1254?

I can only share my point of view :-) I do not see a benefit in mentioning CAs anywhere in the docs anymore when we're about to discontinue support for them soon. We will keep it in the code for own purposes, e.g. debugging, but we want to shift end users to CTFs already right now.

Therefore I would also remove ocm add resources and ocm add sources (and potential other commands forcing the use of CAs) from the documentation / website completely instead of having a warning in the docs. Throwing warnings and give recommendations when people use such commands (because they maybe use an older copied version of the docs, which is already highly hypothetical) is the right way, but in the docs I would try to remove all occurrences of the component archives wherever consistently possible.